\newpage
\section{Requirements}\label{reqs}
This section lists the customer approved requirements and outlines how they have been fulfilled by the project. The sorting reflects the weight of importance appointed to the requirements by the client.

\begin{table}[!h]
\begin{center}%

\begin{tabular}{| p{0.5\textwidth} | p{0.5\textwidth} |}%
\hline%
%\multicolumn{2}{|c|}{#1} \\ % title centered
\sffamily\textbf{Requirement} & \textbf{Fulfilment description} \\ %title as row
\hline%
\sffamily\textbf{The performance and configuration of Data Turbine shall be quickly evaluated.} & In the beginning of the project the features of DataTurbine were examined. Configuration options can be found in the configuration file of SAL-T. Performance values can be found in \autoref{performance}. \\%
\hline%
\sffamily\textbf{The data related to each sensor connected to SAL shall be read and sent to Data Turbine. A sensor can be either one of the following: video, 1-wire sensor, snmp or os data} & All these sensors are supported. \\%
\hline%
\sffamily\textbf{The connection to SAL shall use RMI.} & The SALRMIClient class is used to connect to SAL. It was provided by SAL. \\%
\hline%
\sffamily\textbf{The data sent to DataTurbine shall include metadata, which is in first place the timestamp and the sensor-id.} & Beside the data itself, the timestamp and sensor id provided by the sensor are transmitted through DataTurbine. Furthermore a SAL identifier is added, which can be set in the configuration file. \\%
\hline%
\sffamily\textbf{Sampling rate for sensor data reading shall be configurable depending on the sensor type.} & For each sensor type a thread is being started, which enables the software to poll different sensor types in different intervals. The sampling rate is configurable in the configuration file.\\%
\hline%
\sffamily\textbf{(optional) The connection to SAL shall use local objects/direct communication.} & Because we had to concentrate on the core requirements, this optional requirement was not covered. \\%
\hline%
\end{tabular}%
\end{center}
\caption{Requirements related to the data producer}
\label{tbl:req_producer}
\end{table}

\begin{table}[!h]
\begin{center}%
\begin{tabular}{| p{0.5\textwidth} | p{0.5\textwidth} |}%
\hline%
%\multicolumn{2}{|c|}{#1} \\ % title centered
\sffamily\textbf{Requirement} & \textbf{Fulfilment description} \\ %title as row
\hline%
\sffamily\textbf{Sensor data shall be dumped into the SRB.} & All the data, which is written to DataTurbine is read and dumped to SRB.\\%
\hline%
\sffamily\textbf{The format of the sensor data stored into SRB shall be specified; it shall be optimized for data retrieval.} & As agreed with the customer a structure based on the timestamps and SAL identifier is used to store the data.\\%
\hline%
\sffamily\textbf{The metadata which comes with the sensor data itself shall be stored into SRB.} & The metadata of the received object is used to create the directory and file name of the data\\%
\hline%
\sffamily\textbf{To access SRB the jargon shall be used.} & Due to a customer wish jargon is used to access SRB.\\%
\hline%
\end{tabular}%
\end{center}
\caption{Requirements related to the data consumer}
\label{tbl:req_consumer}
\end{table}

